Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd6cfc82c6c056a8ebed84c04bd0fe49e60a4447a17d335177e4dd25ae7a4584

Tx prefix hash: 2030b2c74222bb8a406977ca39c28e12de14d5ff44fe243c062b9dd4c23e6752
Tx public key: 0d7df4f1a3fa67c8a6002e33143d7aeaedf7d919799fa9b9e2f6492ac8b752bc
Timestamp: 1737853556 Timestamp [UCT]: 2025-01-26 01:05:56 Age [y:d:h:m:s]: 00:147:22:03:36
Block: 1205369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105373 RingCT/type: yes/0
Extra: 010d7df4f1a3fa67c8a6002e33143d7aeaedf7d919799fa9b9e2f6492ac8b752bc0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cf1f00eb43df200de01e4f75ef323d1cb56c575cfd900d0a33861277fa7ee8d 0.600000000000 1692066 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": 1205379, "vin": [ { "gen": { "height": 1205369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cf1f00eb43df200de01e4f75ef323d1cb56c575cfd900d0a33861277fa7ee8d" } } ], "extra": [ 1, 13, 125, 244, 241, 163, 250, 103, 200, 166, 0, 46, 51, 20, 61, 122, 234, 237, 247, 217, 25, 121, 159, 169, 185, 226, 246, 73, 42, 200, 183, 82, 188, 2, 17, 0, 0, 0, 3, 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