Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e14cb455f578f6247ccf69f13c13e46372d7a5af423e14c40b499fc9d4787d34

Tx prefix hash: 3794e03451e0da41515f574a5e15b2b14e6b3dbebf8a251740a46b27edca5480
Tx public key: 9ed83fc127fdf80ad2ed2e3e32848ab4c377caa393c862dc3032848e2c967c9c
Timestamp: 1577197643 Timestamp [UCT]: 2019-12-24 14:27:23 Age [y:d:h:m:s]: 04:339:19:56:14
Block: 30776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132000 RingCT/type: yes/0
Extra: 019ed83fc127fdf80ad2ed2e3e32848ab4c377caa393c862dc3032848e2c967c9c0211000000034943cd9f000000000000000000

1 output(s) for total of 485.318892005000 dcy

stealth address amount amount idx
00: 0ed466e125b73bf59b45e618f5491125a26604f2c6e356c6d16c17775916650e 485.318892005000 50808 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": 30786, "vin": [ { "gen": { "height": 30776 } } ], "vout": [ { "amount": 485318892005, "target": { "key": "0ed466e125b73bf59b45e618f5491125a26604f2c6e356c6d16c17775916650e" } } ], "extra": [ 1, 158, 216, 63, 193, 39, 253, 248, 10, 210, 237, 46, 62, 50, 132, 138, 180, 195, 119, 202, 163, 147, 200, 98, 220, 48, 50, 132, 142, 44, 150, 124, 156, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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