Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14bf13adc4b3dab88a871e21b34102e18e573cd2f939f71336d9a4de33aadbe

Tx prefix hash: ed9ca1ab665198baf158504b9ee0e4901fb7e1d9cb49baa6452a3f12bcfe3203
Tx public key: 3cfa153ea4b35747c21a65b907657258247ff82a1682cb2a2aaf115e84574d05
Timestamp: 1723192910 Timestamp [UCT]: 2024-08-09 08:41:50 Age [y:d:h:m:s]: 01:096:11:22:06
Block: 1084023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327424 RingCT/type: yes/0
Extra: 013cfa153ea4b35747c21a65b907657258247ff82a1682cb2a2aaf115e84574d0502110000000991e13c04000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 33c176206415f56cb6ef55c5562f46fe1a6cdf9e50a7c8054edd12fd6a10a0a8 0.615590000000 1558148 of 0

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": 1084033, "vin": [ { "gen": { "height": 1084023 } } ], "vout": [ { "amount": 615590000, "target": { "key": "33c176206415f56cb6ef55c5562f46fe1a6cdf9e50a7c8054edd12fd6a10a0a8" } } ], "extra": [ 1, 60, 250, 21, 62, 164, 179, 87, 71, 194, 26, 101, 185, 7, 101, 114, 88, 36, 127, 248, 42, 22, 130, 203, 42, 42, 175, 17, 94, 132, 87, 77, 5, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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