Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cbb51997707217f205342c013cfa760edf5e5858d80c1135a03f03a1bece4a6

Tx prefix hash: a48bc7481edec2af3f744b685add47ad8761d52c40eca0e005db777bd59c3c2a
Tx public key: 1a0c4e4e9dc9e3d2ad794dd2d833a14d354643cf9bbc3a157002a82d72f00b9d
Timestamp: 1718844987 Timestamp [UCT]: 2024-06-20 00:56:27 Age [y:d:h:m:s]: 00:287:13:17:26
Block: 1047981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205475 RingCT/type: yes/0
Extra: 011a0c4e4e9dc9e3d2ad794dd2d833a14d354643cf9bbc3a157002a82d72f00b9d0211000000040bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 168fdc41665c0d8f837e7f827735cce1ec87b36511aecb68345638146f89195f 0.600000000000 1517948 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": 1047991, "vin": [ { "gen": { "height": 1047981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "168fdc41665c0d8f837e7f827735cce1ec87b36511aecb68345638146f89195f" } } ], "extra": [ 1, 26, 12, 78, 78, 157, 201, 227, 210, 173, 121, 77, 210, 216, 51, 161, 77, 53, 70, 67, 207, 155, 188, 58, 21, 112, 2, 168, 45, 114, 240, 11, 157, 2, 17, 0, 0, 0, 4, 11, 186, 22, 215, 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