Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85c9bd8095bf1fd7bc9736de73b9b42aeafd57f179138543e94cec2636e52d8f

Tx prefix hash: ab9dbc794025871db59bd3f1d826dc649601e34855871f64418d1f76e5e853e1
Tx public key: 44109c262980867e53764a51892f41c0ce7e73e2b839714ee6f417cc8abcef0d
Timestamp: 1575382590 Timestamp [UCT]: 2019-12-03 14:16:30 Age [y:d:h:m:s]: 04:359:21:23:09
Block: 21264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1140825 RingCT/type: yes/0
Extra: 0144109c262980867e53764a51892f41c0ce7e73e2b839714ee6f417cc8abcef0d020d39303031000100000042c89603

1 output(s) for total of 521.848471644000 dcy

stealth address amount amount idx
00: 158e66ed3564ecfb6f810744859d91b33a7c6fe3f1f2713faea9fe80744cbfe8 521.848471644000 33909 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": 21274, "vin": [ { "gen": { "height": 21264 } } ], "vout": [ { "amount": 521848471644, "target": { "key": "158e66ed3564ecfb6f810744859d91b33a7c6fe3f1f2713faea9fe80744cbfe8" } } ], "extra": [ 1, 68, 16, 156, 38, 41, 128, 134, 126, 83, 118, 74, 81, 137, 47, 65, 192, 206, 126, 115, 226, 184, 57, 113, 78, 230, 244, 23, 204, 138, 188, 239, 13, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 66, 200, 150, 3 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8