Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3dd68672ba3b2e0c21fb7816616fd481b58bca17048a0a2ef2f3c6e3cbd84a9

Tx prefix hash: 5f365669341b259a135747e9e9f62e30b91d86a4831cc36f84b9d2843221ee9a
Tx public key: 8cf7e7f1e9aae668fb0235f21c1639a5c897ee4e9281adb989393a1b3269494f
Timestamp: 1593018139 Timestamp [UCT]: 2020-06-24 17:02:19 Age [y:d:h:m:s]: 04:323:04:49:00
Block: 110530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171055 RingCT/type: yes/0
Extra: 018cf7e7f1e9aae668fb0235f21c1639a5c897ee4e9281adb989393a1b3269494f02110000001646a11e8a000000000000000000

1 output(s) for total of 264.100348371000 dcy

stealth address amount amount idx
00: 9a15ecce670b3123d26951ead4dd92af764576a85fd2fcf2aed9eea40a1526e3 264.100348371000 191416 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": 110540, "vin": [ { "gen": { "height": 110530 } } ], "vout": [ { "amount": 264100348371, "target": { "key": "9a15ecce670b3123d26951ead4dd92af764576a85fd2fcf2aed9eea40a1526e3" } } ], "extra": [ 1, 140, 247, 231, 241, 233, 170, 230, 104, 251, 2, 53, 242, 28, 22, 57, 165, 200, 151, 238, 78, 146, 129, 173, 185, 137, 57, 58, 27, 50, 105, 73, 79, 2, 17, 0, 0, 0, 22, 70, 161, 30, 138, 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