Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7556da6fd653b406452fd4ed773aca8753ffe5410b0df74a4d5624725e309448

Tx prefix hash: 42ac8ed19607eff35310d04e8d9e4b6359493255789aabf0812c3a117bad120b
Tx public key: 3c01c8c58d1744e9c43434c238fe631ff3a0f2c8675b94f2d729dc87780ba514
Timestamp: 1741244105 Timestamp [UCT]: 2025-03-06 06:55:05 Age [y:d:h:m:s]: 00:006:11:01:13
Block: 1233219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4632 RingCT/type: yes/0
Extra: 013c01c8c58d1744e9c43434c238fe631ff3a0f2c8675b94f2d729dc87780ba5140211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e8cae1670e29d4a2fd90ae4769a96d5490ea4b9a3156f5943d326ff46b3ac2b 0.600000000000 1720138 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": 1233229, "vin": [ { "gen": { "height": 1233219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e8cae1670e29d4a2fd90ae4769a96d5490ea4b9a3156f5943d326ff46b3ac2b" } } ], "extra": [ 1, 60, 1, 200, 197, 141, 23, 68, 233, 196, 52, 52, 194, 56, 254, 99, 31, 243, 160, 242, 200, 103, 91, 148, 242, 215, 41, 220, 135, 120, 11, 165, 20, 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