Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f243ba71327ee832487401e9d7d97c41a255d66e1c2136763b1959a590f365

Tx prefix hash: 0bff25d91159121ac0fbd8bca5644812a7cfd4dd920e88fc9e22a861de05b2a3
Tx public key: 7add8e5e45f9d937e49bcf2ac08a817a3749b7fbfb2379349da87dbf9874bc78
Timestamp: 1624995763 Timestamp [UCT]: 2021-06-29 19:42:43 Age [y:d:h:m:s]: 03:149:13:40:26
Block: 285456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 875850 RingCT/type: yes/0
Extra: 017add8e5e45f9d937e49bcf2ac08a817a3749b7fbfb2379349da87dbf9874bc7802110000001299438644000000000000000000

1 output(s) for total of 69.529048331000 dcy

stealth address amount amount idx
00: 63a5be2ab8d9152de1cd77fd0a6853ecfad4369cb77448dc5436cc3108611dc8 69.529048331000 597661 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": 285466, "vin": [ { "gen": { "height": 285456 } } ], "vout": [ { "amount": 69529048331, "target": { "key": "63a5be2ab8d9152de1cd77fd0a6853ecfad4369cb77448dc5436cc3108611dc8" } } ], "extra": [ 1, 122, 221, 142, 94, 69, 249, 217, 55, 228, 155, 207, 42, 192, 138, 129, 122, 55, 73, 183, 251, 251, 35, 121, 52, 157, 168, 125, 191, 152, 116, 188, 120, 2, 17, 0, 0, 0, 18, 153, 67, 134, 68, 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