Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74fd750c30c1b8ad3b7ef1c95ccfdffa1cca0c19a974c78a62b30ad3e8bcc654

Tx prefix hash: 978bf7c7c7aded50e630693907eb832620f136caf8174ec08e963f7a136cf7c0
Tx public key: f5f258952742973e0b96371f2d7986f50c8284122f423133ec59cc502588b111
Timestamp: 1663460224 Timestamp [UCT]: 2022-09-18 00:17:04 Age [y:d:h:m:s]: 02:186:08:42:55
Block: 590233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654495 RingCT/type: yes/0
Extra: 01f5f258952742973e0b96371f2d7986f50c8284122f423133ec59cc502588b111021100000001143619d6000000000000000000

1 output(s) for total of 6.796935172000 dcy

stealth address amount amount idx
00: 7abf8dd2d31e9b0634f809e1081b0b84fda7fdbc932714a79a503fac2cbcafb2 6.796935172000 1024628 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": 590243, "vin": [ { "gen": { "height": 590233 } } ], "vout": [ { "amount": 6796935172, "target": { "key": "7abf8dd2d31e9b0634f809e1081b0b84fda7fdbc932714a79a503fac2cbcafb2" } } ], "extra": [ 1, 245, 242, 88, 149, 39, 66, 151, 62, 11, 150, 55, 31, 45, 121, 134, 245, 12, 130, 132, 18, 47, 66, 49, 51, 236, 89, 204, 80, 37, 136, 177, 17, 2, 17, 0, 0, 0, 1, 20, 54, 25, 214, 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