Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5572f8fca5d2ed2d609d7639f8c54b0a3884e7ee60b757695a99bf0bd591aec2

Tx prefix hash: 8851220432fca9c202199bd64db324c488e822b3dd0567a3f7c916443acc9c4a
Tx public key: 6ef1b0f3a18e9b534a800b5040ad9a3fe83bd4de2bf4d24d0216b13590ef1702
Timestamp: 1737781532 Timestamp [UCT]: 2025-01-25 05:05:32 Age [y:d:h:m:s]: 00:144:08:35:22
Block: 1204781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102894 RingCT/type: yes/0
Extra: 016ef1b0f3a18e9b534a800b5040ad9a3fe83bd4de2bf4d24d0216b13590ef1702021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f4024051a9fa765f5298f9cd07249a7c0c36f610f996561099dcb2ba81f40d2 0.600000000000 1691474 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": 1204791, "vin": [ { "gen": { "height": 1204781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f4024051a9fa765f5298f9cd07249a7c0c36f610f996561099dcb2ba81f40d2" } } ], "extra": [ 1, 110, 241, 176, 243, 161, 142, 155, 83, 74, 128, 11, 80, 64, 173, 154, 63, 232, 59, 212, 222, 43, 244, 210, 77, 2, 22, 177, 53, 144, 239, 23, 2, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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