Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f03b141c7429dc1071a4d0825e2ffbd6bf24c355c4be92bde213a3fa80f49a

Tx prefix hash: b51c992778855881da717e2e30b78563d8f21173bfc464774a7e7197a4a5b9f1
Tx public key: d866a056e4c85bac3b9f2d85fc24d6303822c2e27ce141d2bf04f1ebce6fc2f3
Timestamp: 1617645484 Timestamp [UCT]: 2021-04-05 17:58:04 Age [y:d:h:m:s]: 03:277:22:05:48
Block: 233858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 958414 RingCT/type: yes/0
Extra: 01d866a056e4c85bac3b9f2d85fc24d6303822c2e27ce141d2bf04f1ebce6fc2f302110000000d3a645b90000000000000000000

1 output(s) for total of 103.069920929000 dcy

stealth address amount amount idx
00: 6933f6a2c2e3b877e8ed3acd7e6ee046d63e50eaac67968ed0350852f862730a 103.069920929000 485544 of 0

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": 233868, "vin": [ { "gen": { "height": 233858 } } ], "vout": [ { "amount": 103069920929, "target": { "key": "6933f6a2c2e3b877e8ed3acd7e6ee046d63e50eaac67968ed0350852f862730a" } } ], "extra": [ 1, 216, 102, 160, 86, 228, 200, 91, 172, 59, 159, 45, 133, 252, 36, 214, 48, 56, 34, 194, 226, 124, 225, 65, 210, 191, 4, 241, 235, 206, 111, 194, 243, 2, 17, 0, 0, 0, 13, 58, 100, 91, 144, 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