Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fc9149da15497ec25f8ddf79c39d8f2ad8a8afa9e6cc0b69ce7cdb69039569

Tx prefix hash: 20b375ce5991ab8028b7ce28650c3f86934ae7199d1f2a2d10796a4a604066c5
Tx public key: 46cd4eb861afda3a785f80445b7dc3b386c8c00a048228b9d37620c2c37b8cc3
Timestamp: 1720021131 Timestamp [UCT]: 2024-07-03 15:38:51 Age [y:d:h:m:s]: 00:274:09:41:23
Block: 1057732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196059 RingCT/type: yes/0
Extra: 0146cd4eb861afda3a785f80445b7dc3b386c8c00a048228b9d37620c2c37b8cc30211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e5f3774a8050762035e0023d30f97856e14c49ab75c7405fc59540ff1b6fc71 0.600000000000 1528173 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": 1057742, "vin": [ { "gen": { "height": 1057732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5f3774a8050762035e0023d30f97856e14c49ab75c7405fc59540ff1b6fc71" } } ], "extra": [ 1, 70, 205, 78, 184, 97, 175, 218, 58, 120, 95, 128, 68, 91, 125, 195, 179, 134, 200, 192, 10, 4, 130, 40, 185, 211, 118, 32, 194, 195, 123, 140, 195, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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