Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36718e3b3238af699ae30434221a862de752e727ac666420b2a352735b8dc2d7

Tx prefix hash: a72bda51001312f4edc379be28cab8a612989cb4cc16447a6db52fdb20ccd926
Tx public key: 06f3e827092e8a8a539235f601469cb0af99662ab8391ca703ab82338584ec8a
Timestamp: 1745227120 Timestamp [UCT]: 2025-04-21 09:18:40 Age [y:d:h:m:s]: 00:213:13:08:04
Block: 1266180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150350 RingCT/type: yes/0
Extra: 0106f3e827092e8a8a539235f601469cb0af99662ab8391ca703ab82338584ec8a021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8559a4c4cc1bf4e9de8b8d5f98eb42b5469ab06d810e9f971a8d02a3e5e5e8e 0.600000000000 1753397 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": 1266190, "vin": [ { "gen": { "height": 1266180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8559a4c4cc1bf4e9de8b8d5f98eb42b5469ab06d810e9f971a8d02a3e5e5e8e" } } ], "extra": [ 1, 6, 243, 232, 39, 9, 46, 138, 138, 83, 146, 53, 246, 1, 70, 156, 176, 175, 153, 102, 42, 184, 57, 28, 167, 3, 171, 130, 51, 133, 132, 236, 138, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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