Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12e1b69efe06da74cde2eef937c15a65a5ef9b506e382a6087d3256b1980668a

Tx prefix hash: 35074deefa6b3969dfe009cd6be6bc3f4359aca81f40cd59cec61f76e394ceee
Tx public key: 031d844a33c0f2b3da75cd07aa2b1aa2f6c0ca4ad03822d0ffea2ce08a1f8ad4
Timestamp: 1714495141 Timestamp [UCT]: 2024-04-30 16:39:01 Age [y:d:h:m:s]: 01:046:11:22:17
Block: 1011921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294072 RingCT/type: yes/0
Extra: 01031d844a33c0f2b3da75cd07aa2b1aa2f6c0ca4ad03822d0ffea2ce08a1f8ad402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37da349dc858263552ccf5be3c4eae7c3271f039c50e3c1b7e75c76aeef0030b 0.600000000000 1474283 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": 1011931, "vin": [ { "gen": { "height": 1011921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37da349dc858263552ccf5be3c4eae7c3271f039c50e3c1b7e75c76aeef0030b" } } ], "extra": [ 1, 3, 29, 132, 74, 51, 192, 242, 179, 218, 117, 205, 7, 170, 43, 26, 162, 246, 192, 202, 74, 208, 56, 34, 208, 255, 234, 44, 224, 138, 31, 138, 212, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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