Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c47032934419cf9cc3cad52711a15e15cadc0222c143475feed86bc6c7c1999f

Tx prefix hash: c5b49883c42e8bd7061d63556817d69fe8fd7f482c0c3daf172848b78020c4de
Tx public key: 0f7455f1b9bc504707f81fbb2cd2ae8744a004c4f1ff46f9467ef55db580ad65
Timestamp: 1700867129 Timestamp [UCT]: 2023-11-24 23:05:29 Age [y:d:h:m:s]: 01:097:14:13:55
Block: 898936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330886 RingCT/type: yes/0
Extra: 010f7455f1b9bc504707f81fbb2cd2ae8744a004c4f1ff46f9467ef55db580ad6502110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.644839824000 dcy

stealth address amount amount idx
00: 1f1cde10fa7a3e4f26d0f846021bf83a5d387d0934917656a5e25dc28b13827a 0.644839824000 1355373 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": 898946, "vin": [ { "gen": { "height": 898936 } } ], "vout": [ { "amount": 644839824, "target": { "key": "1f1cde10fa7a3e4f26d0f846021bf83a5d387d0934917656a5e25dc28b13827a" } } ], "extra": [ 1, 15, 116, 85, 241, 185, 188, 80, 71, 7, 248, 31, 187, 44, 210, 174, 135, 68, 160, 4, 196, 241, 255, 70, 249, 70, 126, 245, 93, 181, 128, 173, 101, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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