Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41ac2cbf29d4520df2b48a3bc51aa48ba27cbcbb0c8963fbfd4972f41d556641

Tx prefix hash: fad6c0f644cf13cb58a99cb4613d63253ecf488750356a2ce035fd1fc5bfe4ff
Tx public key: 32eb26303160d477815fd1d54c0f174dfb7ae5a1524bcc804af193c274610878
Timestamp: 1701205462 Timestamp [UCT]: 2023-11-28 21:04:22 Age [y:d:h:m:s]: 01:132:07:15:58
Block: 901742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355711 RingCT/type: yes/0
Extra: 0132eb26303160d477815fd1d54c0f174dfb7ae5a1524bcc804af193c27461087802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.631181707000 dcy

stealth address amount amount idx
00: 46f92ecd855bd180e323b53491e44334b1f45fb835fec8280dbd7ee8071dde5a 0.631181707000 1358331 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": 901752, "vin": [ { "gen": { "height": 901742 } } ], "vout": [ { "amount": 631181707, "target": { "key": "46f92ecd855bd180e323b53491e44334b1f45fb835fec8280dbd7ee8071dde5a" } } ], "extra": [ 1, 50, 235, 38, 48, 49, 96, 212, 119, 129, 95, 209, 213, 76, 15, 23, 77, 251, 122, 229, 161, 82, 75, 204, 128, 74, 241, 147, 194, 116, 97, 8, 120, 2, 17, 0, 0, 0, 2, 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