Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33b7d65f4caae04383aa61ef3c6ec9b1e505afa3afdda3d1d1c107257fe2b6b

Tx prefix hash: 5921fa30813941c89a786562e7bd31e2c1007127e9d6c50fe961a711c0012da4
Tx public key: 6d16e704d815ace7cbda8e9d4cfde6892331bc43f79f84c4f28f8f56b11bb615
Timestamp: 1672144870 Timestamp [UCT]: 2022-12-27 12:41:10 Age [y:d:h:m:s]: 01:340:19:57:36
Block: 661689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504609 RingCT/type: yes/0
Extra: 016d16e704d815ace7cbda8e9d4cfde6892331bc43f79f84c4f28f8f56b11bb61502110000000133af99f4000000000000000000

1 output(s) for total of 3.940484579000 dcy

stealth address amount amount idx
00: 10858a3154fa17db1ef20ffce4f6cb907874898220fa2b24e2fdf9ec8a93d2b1 3.940484579000 1102482 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": 661699, "vin": [ { "gen": { "height": 661689 } } ], "vout": [ { "amount": 3940484579, "target": { "key": "10858a3154fa17db1ef20ffce4f6cb907874898220fa2b24e2fdf9ec8a93d2b1" } } ], "extra": [ 1, 109, 22, 231, 4, 216, 21, 172, 231, 203, 218, 142, 157, 76, 253, 230, 137, 35, 49, 188, 67, 247, 159, 132, 196, 242, 143, 143, 86, 177, 27, 182, 21, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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