Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b63557f57dc9b225bd78c3f78084d4380d65145c7368f0194212de7c892e3de

Tx prefix hash: 9e2b0fe880c7635c2fcbfd746c7fcd07bf6b753500f74a47a6f03a731ed2d6dd
Tx public key: 4615e9fbc23a47f98e72dcc74659d23d9020bba4cf2abd4d18d1fae5ed1bbce4
Timestamp: 1735398724 Timestamp [UCT]: 2024-12-28 15:12:04 Age [y:d:h:m:s]: 00:095:07:15:34
Block: 1185080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67903 RingCT/type: yes/0
Extra: 014615e9fbc23a47f98e72dcc74659d23d9020bba4cf2abd4d18d1fae5ed1bbce40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 343fedb72e76587c10618a319f329d3d6df904038e262ee7570e9a6406764dea 0.600000000000 1671545 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": 1185090, "vin": [ { "gen": { "height": 1185080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "343fedb72e76587c10618a319f329d3d6df904038e262ee7570e9a6406764dea" } } ], "extra": [ 1, 70, 21, 233, 251, 194, 58, 71, 249, 142, 114, 220, 199, 70, 89, 210, 61, 144, 32, 187, 164, 207, 42, 189, 77, 24, 209, 250, 229, 237, 27, 188, 228, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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