Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512d61ae3bf2a987b36b232bed4c0e2a0b0be3554b08fc1020aadb36d7b445dd

Tx prefix hash: 76d6100fcf1e0211d0f31bb1a3ded74869c93cf772d49eecfbe88f20bec028c6
Tx public key: 338cb34babe0bc3b38471da5e4312c7c404eeb78d6cc6d17bfd3e22ff9d61f0c
Timestamp: 1670089664 Timestamp [UCT]: 2022-12-03 17:47:44 Age [y:d:h:m:s]: 02:119:01:48:35
Block: 644668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606807 RingCT/type: yes/0
Extra: 01338cb34babe0bc3b38471da5e4312c7c404eeb78d6cc6d17bfd3e22ff9d61f0c02110000000183600029000000000000000000

1 output(s) for total of 4.486909355000 dcy

stealth address amount amount idx
00: a2aebaaa8aca7689b80f7aa541eede7ab12015d966afec6b280fc3a9fe014e52 4.486909355000 1084735 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": 644678, "vin": [ { "gen": { "height": 644668 } } ], "vout": [ { "amount": 4486909355, "target": { "key": "a2aebaaa8aca7689b80f7aa541eede7ab12015d966afec6b280fc3a9fe014e52" } } ], "extra": [ 1, 51, 140, 179, 75, 171, 224, 188, 59, 56, 71, 29, 165, 228, 49, 44, 124, 64, 78, 235, 120, 214, 204, 109, 23, 191, 211, 226, 47, 249, 214, 31, 12, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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