Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd40994ebda249c5f7cdb5c070835649f1b1d0353144d98d05c8d28c15cd052c

Tx prefix hash: 1d121afdd2a749e52bf562ef5816c30a86ab8c5a7f101012c70512245483852f
Tx public key: 9e0e4cdccda32350f3d06d484a39fe194237d4d3bd7f2f3930d14b7b3abc0085
Timestamp: 1728301440 Timestamp [UCT]: 2024-10-07 11:44:00 Age [y:d:h:m:s]: 00:209:18:50:31
Block: 1126384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149734 RingCT/type: yes/0
Extra: 019e0e4cdccda32350f3d06d484a39fe194237d4d3bd7f2f3930d14b7b3abc0085021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c303bbe51f69034cb9346a899549a0764d48abc0f7d8a0ae826b1392dde68bd 0.600000000000 1609175 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": 1126394, "vin": [ { "gen": { "height": 1126384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c303bbe51f69034cb9346a899549a0764d48abc0f7d8a0ae826b1392dde68bd" } } ], "extra": [ 1, 158, 14, 76, 220, 205, 163, 35, 80, 243, 208, 109, 72, 74, 57, 254, 25, 66, 55, 212, 211, 189, 127, 47, 57, 48, 209, 75, 123, 58, 188, 0, 133, 2, 17, 0, 0, 0, 2, 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