Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf81d4f4b909c4abe654ff7f8ca5e7351ef0808859726a7a44f70f5f91921c3b

Tx prefix hash: 5013cd4e9bc689bf6da7b5735d0211db07a0777596a951e92486c650f10d93ef
Tx public key: daa517fc6afdcd4229765c5a3ac2070aa798f54209dfebea60727f3e351493a3
Timestamp: 1622458085 Timestamp [UCT]: 2021-05-31 10:48:05 Age [y:d:h:m:s]: 03:161:08:05:01
Block: 269767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 878950 RingCT/type: yes/0
Extra: 01daa517fc6afdcd4229765c5a3ac2070aa798f54209dfebea60727f3e351493a302110000002967297a1c000000000000000000

1 output(s) for total of 78.370113814000 dcy

stealth address amount amount idx
00: 2d4f23379f0253173074b13bfc0a1bb94f978ce30b7f33dbb742bb834ea01c0e 78.370113814000 566173 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": 269777, "vin": [ { "gen": { "height": 269767 } } ], "vout": [ { "amount": 78370113814, "target": { "key": "2d4f23379f0253173074b13bfc0a1bb94f978ce30b7f33dbb742bb834ea01c0e" } } ], "extra": [ 1, 218, 165, 23, 252, 106, 253, 205, 66, 41, 118, 92, 90, 58, 194, 7, 10, 167, 152, 245, 66, 9, 223, 235, 234, 96, 114, 127, 62, 53, 20, 147, 163, 2, 17, 0, 0, 0, 41, 103, 41, 122, 28, 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