Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abea145b7d36e610576f16c1f90615e8591e52dd5f71afa11864952c896e8354

Tx prefix hash: b8aaa48ea656f696d579e7b0e2c3d1bd1a2889ecb2c91bd1be3a1870e8b92166
Tx public key: 077521fb3f69e00f7baa5ce8469b16c07ab871030203b1cecc01cefc29f10990
Timestamp: 1645032543 Timestamp [UCT]: 2022-02-16 17:29:03 Age [y:d:h:m:s]: 03:058:17:56:01
Block: 439998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 821955 RingCT/type: yes/0
Extra: 01077521fb3f69e00f7baa5ce8469b16c07ab871030203b1cecc01cefc29f1099002110000000b2e6b1fd5000000000000000000

1 output(s) for total of 21.384754436000 dcy

stealth address amount amount idx
00: 6b2bf2b7c1a906566cc7fed15ec9fe4efc60a24c2eaef682438a8d33c99ccb1b 21.384754436000 852253 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": 440008, "vin": [ { "gen": { "height": 439998 } } ], "vout": [ { "amount": 21384754436, "target": { "key": "6b2bf2b7c1a906566cc7fed15ec9fe4efc60a24c2eaef682438a8d33c99ccb1b" } } ], "extra": [ 1, 7, 117, 33, 251, 63, 105, 224, 15, 123, 170, 92, 232, 70, 155, 22, 192, 122, 184, 113, 3, 2, 3, 177, 206, 204, 1, 206, 252, 41, 241, 9, 144, 2, 17, 0, 0, 0, 11, 46, 107, 31, 213, 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