Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d45f5051f6a1e788387714bfeb37e23f93f6b2049eaf173e0c3feb818252ccd

Tx prefix hash: 740f11b2a564d9655814a992f3a3b8c78fa81ddcc3c54b0c82cd892030bc1089
Tx public key: 86c77b42dea57c6af0ca85fbfebb3370e4f115e3b725d636b27e176bce9f2d61
Timestamp: 1717406459 Timestamp [UCT]: 2024-06-03 09:20:59 Age [y:d:h:m:s]: 00:318:19:08:53
Block: 1036067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227833 RingCT/type: yes/0
Extra: 0186c77b42dea57c6af0ca85fbfebb3370e4f115e3b725d636b27e176bce9f2d6102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f3b6cf9646374e4dded14c600b7dee9fc05b9e092113d90f4dcdc7e97490f8 0.600000000000 1504592 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": 1036077, "vin": [ { "gen": { "height": 1036067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f3b6cf9646374e4dded14c600b7dee9fc05b9e092113d90f4dcdc7e97490f8" } } ], "extra": [ 1, 134, 199, 123, 66, 222, 165, 124, 106, 240, 202, 133, 251, 254, 187, 51, 112, 228, 241, 21, 227, 183, 37, 214, 54, 178, 126, 23, 107, 206, 159, 45, 97, 2, 17, 0, 0, 0, 3, 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