Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9291f48d4573e9974f8d5eb387346a254d8d3132673e55c3e955fb2e81e28e9b

Tx prefix hash: eeb510d01a9f1e631f3ca3924f7aa8459e277a654a353d3f3cc5f75a1a98c53c
Tx public key: f8a88a9e924329af522402d4be51e8aecfba93d45ef7fcbae01d551b7af584e9
Timestamp: 1582337200 Timestamp [UCT]: 2020-02-22 02:06:40 Age [y:d:h:m:s]: 04:278:20:25:03
Block: 69901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091800 RingCT/type: yes/0
Extra: 01f8a88a9e924329af522402d4be51e8aecfba93d45ef7fcbae01d551b7af584e902110000000112c4732d000000000000000000

1 output(s) for total of 360.072350343000 dcy

stealth address amount amount idx
00: 449da808074ca9729f56879940c8da8c6ae06069b1d39e56c79a5514b8f1ac53 360.072350343000 129004 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": 69911, "vin": [ { "gen": { "height": 69901 } } ], "vout": [ { "amount": 360072350343, "target": { "key": "449da808074ca9729f56879940c8da8c6ae06069b1d39e56c79a5514b8f1ac53" } } ], "extra": [ 1, 248, 168, 138, 158, 146, 67, 41, 175, 82, 36, 2, 212, 190, 81, 232, 174, 207, 186, 147, 212, 94, 247, 252, 186, 224, 29, 85, 27, 122, 245, 132, 233, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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