Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a14143635d0d606fa58aee831053d716d0704b0334e999bb03df6c4e6232c867

Tx prefix hash: bdd19bab98dfb14973c57bf11fac981da84ed72cd1de772709ab10359a4cdcc3
Tx public key: 8cd4ff25c5f3b217f6e7857f590fa7569d623a0c03aa13b8e577b74aea3b2372
Timestamp: 1713921608 Timestamp [UCT]: 2024-04-24 01:20:08 Age [y:d:h:m:s]: 00:359:08:10:29
Block: 1007158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256898 RingCT/type: yes/0
Extra: 018cd4ff25c5f3b217f6e7857f590fa7569d623a0c03aa13b8e577b74aea3b23720211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9bb88aa464b5ee95a4281c14e4ee2980fc0a0e0757a6ba72621e04eab43f4e6 0.600000000000 1468408 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": 1007168, "vin": [ { "gen": { "height": 1007158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9bb88aa464b5ee95a4281c14e4ee2980fc0a0e0757a6ba72621e04eab43f4e6" } } ], "extra": [ 1, 140, 212, 255, 37, 197, 243, 178, 23, 246, 231, 133, 127, 89, 15, 167, 86, 157, 98, 58, 12, 3, 170, 19, 184, 229, 119, 183, 74, 234, 59, 35, 114, 2, 17, 0, 0, 0, 1, 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