Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b409eebb09aee284f68e36e65a1eb1d97a34758d0b231f65c8a84fcf4a28a5ba

Tx prefix hash: 705271ca40c1cad89283407b55ced7ffd056c80421a324168578e04556087129
Tx public key: 635f60c057ca6f345eaa5edf396f7642a4f979745fe17dc50709420e45a48b2b
Timestamp: 1726536706 Timestamp [UCT]: 2024-09-17 01:31:46 Age [y:d:h:m:s]: 00:201:21:26:52
Block: 1111749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144104 RingCT/type: yes/0
Extra: 01635f60c057ca6f345eaa5edf396f7642a4f979745fe17dc50709420e45a48b2b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eec3ac9fcf9d7eba7dbcf8c056eee8c57e5184f19b73943e9d183cd17291a0b 0.600000000000 1590818 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1111759, "vin": [ { "gen": { "height": 1111749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eec3ac9fcf9d7eba7dbcf8c056eee8c57e5184f19b73943e9d183cd17291a0b" } } ], "extra": [ 1, 99, 95, 96, 192, 87, 202, 111, 52, 94, 170, 94, 223, 57, 111, 118, 66, 164, 249, 121, 116, 95, 225, 125, 197, 7, 9, 66, 14, 69, 164, 139, 43, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8