Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b12a6bb6b268e0a36af29de64d5d49f9743af2d79402fcff381cb4b3da879167

Tx prefix hash: c1ef665a4b810430dfb866ea56097d4cf9d4ff6cfb1d4a83a59e2770e1d08b38
Tx public key: d74f7375518fcb5898893703f22b630b51fc87e7bb6af2aa4059527016e42b46
Timestamp: 1751080935 Timestamp [UCT]: 2025-06-28 03:22:15 Age [y:d:h:m:s]: 00:141:01:08:50
Block: 1314257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98882 RingCT/type: yes/0
Extra: 01d74f7375518fcb5898893703f22b630b51fc87e7bb6af2aa4059527016e42b4602110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e69fd1f941e18e082b4d40465be0cd6d31f3a7d5a8804878093facd3e9a0a0 0.600000000000 1801902 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": 1314267, "vin": [ { "gen": { "height": 1314257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e69fd1f941e18e082b4d40465be0cd6d31f3a7d5a8804878093facd3e9a0a0" } } ], "extra": [ 1, 215, 79, 115, 117, 81, 143, 203, 88, 152, 137, 55, 3, 242, 43, 99, 11, 81, 252, 135, 231, 187, 106, 242, 170, 64, 89, 82, 112, 22, 228, 43, 70, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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