Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea25e51a20ced92138f492340d49b7ef661a7b81e6156071b8bef622956d28b7

Tx prefix hash: d74ff6793ee5b4417f95c0e303a1b7518e920e2ad61532d4e0d0cff9f9f69486
Tx public key: 6d4cf8b572e6d492fa88c6d22c99f0002ceaa3fb7281eaef0e2ec3524015fbe0
Timestamp: 1737139543 Timestamp [UCT]: 2025-01-17 18:45:43 Age [y:d:h:m:s]: 00:152:01:26:29
Block: 1199500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108363 RingCT/type: yes/0
Extra: 016d4cf8b572e6d492fa88c6d22c99f0002ceaa3fb7281eaef0e2ec3524015fbe00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a880a1ec1307ce2904a7c7f31625901433920b1cdfd0f1728c9acb31526f9a 0.600000000000 1686131 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": 1199510, "vin": [ { "gen": { "height": 1199500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a880a1ec1307ce2904a7c7f31625901433920b1cdfd0f1728c9acb31526f9a" } } ], "extra": [ 1, 109, 76, 248, 181, 114, 230, 212, 146, 250, 136, 198, 210, 44, 153, 240, 0, 44, 234, 163, 251, 114, 129, 234, 239, 14, 46, 195, 82, 64, 21, 251, 224, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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