Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d07aa89746e87543b03c47d653838c734d4b93f43e7ddf4036c681cf384b2c

Tx prefix hash: 06ac40a56d055c59e35e7b146f959e4de66ab3b73372b6cbebda0c8a8842df84
Tx public key: bacdec8a1a8e6da8c3740fc237f82d6b13c2f7c8533a43cd8a5c964efef6f25b
Timestamp: 1673446284 Timestamp [UCT]: 2023-01-11 14:11:24 Age [y:d:h:m:s]: 02:101:22:54:03
Block: 672469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594548 RingCT/type: yes/0
Extra: 01bacdec8a1a8e6da8c3740fc237f82d6b13c2f7c8533a43cd8a5c964efef6f25b02110000000652542ceb000000000000000000

1 output(s) for total of 3.629367964000 dcy

stealth address amount amount idx
00: b025d0c28de0d47f5e49ea9ebef9c79ec94fe3ade22f685d7bdddcb400ff221d 3.629367964000 1114020 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": 672479, "vin": [ { "gen": { "height": 672469 } } ], "vout": [ { "amount": 3629367964, "target": { "key": "b025d0c28de0d47f5e49ea9ebef9c79ec94fe3ade22f685d7bdddcb400ff221d" } } ], "extra": [ 1, 186, 205, 236, 138, 26, 142, 109, 168, 195, 116, 15, 194, 55, 248, 45, 107, 19, 194, 247, 200, 83, 58, 67, 205, 138, 92, 150, 78, 254, 246, 242, 91, 2, 17, 0, 0, 0, 6, 82, 84, 44, 235, 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