Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5549a27eb2e52e4c5da00fc29f0c29c4602389f73add03bc47b75fd278cf4224

Tx prefix hash: 83e29f9f46e680fba39ef03f281d65ee91b203b9958d369dc80516443fed7ed3
Tx public key: f1fb50f8240b9c017132f88d704337a0ec1e2ddfef8bd64c53adf36c5e3db8db
Timestamp: 1724877422 Timestamp [UCT]: 2024-08-28 20:37:02 Age [y:d:h:m:s]: 00:134:17:04:21
Block: 1097984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96361 RingCT/type: yes/0
Extra: 01f1fb50f8240b9c017132f88d704337a0ec1e2ddfef8bd64c53adf36c5e3db8db02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a67b3953f7ba7cf1507fb8696abc46fb89addd1a41beb852a691b93a2af73cb 0.600000000000 1573545 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": 1097994, "vin": [ { "gen": { "height": 1097984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a67b3953f7ba7cf1507fb8696abc46fb89addd1a41beb852a691b93a2af73cb" } } ], "extra": [ 1, 241, 251, 80, 248, 36, 11, 156, 1, 113, 50, 248, 141, 112, 67, 55, 160, 236, 30, 45, 223, 239, 139, 214, 76, 83, 173, 243, 108, 94, 61, 184, 219, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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