Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd0988c03794ab48a01ad912f78911a4ed6fc92a92e48196937f427fd1e1e5b

Tx prefix hash: 652252420d87bb48c28c83a9c2db415a34de64a84e03ee29123b1019837093a3
Tx public key: dd751c68e1960b9a02d8b2495d3ffc9f97408d9a8822100d46cd1f4f2ece62b8
Timestamp: 1720020489 Timestamp [UCT]: 2024-07-03 15:28:09 Age [y:d:h:m:s]: 00:254:08:05:04
Block: 1057729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181721 RingCT/type: yes/0
Extra: 01dd751c68e1960b9a02d8b2495d3ffc9f97408d9a8822100d46cd1f4f2ece62b802110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f2d2c575d0cba8fe57d9ec609d32e30b46392db457cf55157372de64e6077e4 0.600000000000 1528170 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": 1057739, "vin": [ { "gen": { "height": 1057729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f2d2c575d0cba8fe57d9ec609d32e30b46392db457cf55157372de64e6077e4" } } ], "extra": [ 1, 221, 117, 28, 104, 225, 150, 11, 154, 2, 216, 178, 73, 93, 63, 252, 159, 151, 64, 141, 154, 136, 34, 16, 13, 70, 205, 31, 79, 46, 206, 98, 184, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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