Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afab92507acb74169330fb3df85100f39fd32acb066b0e60e22e7e83c1fca3f4

Tx prefix hash: 1164215777f9988a37633df79ffd08052f88776af50e5f351c87a3c86c95c9d8
Tx public key: 70d1426f8222f3beabdc656f034315c4a17727a56b23cdee6f10200e2844edd6
Timestamp: 1577815846 Timestamp [UCT]: 2019-12-31 18:10:46 Age [y:d:h:m:s]: 04:333:00:32:40
Block: 35929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127093 RingCT/type: yes/0
Extra: 0170d1426f8222f3beabdc656f034315c4a17727a56b23cdee6f10200e2844edd60211000000334943cd9f000000000000000000

1 output(s) for total of 466.643804266000 dcy

stealth address amount amount idx
00: 72c49ee4d0b119446c17de8cc238855847dfe2c394cecee62da90afd5c8f3d9b 466.643804266000 60689 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": 35939, "vin": [ { "gen": { "height": 35929 } } ], "vout": [ { "amount": 466643804266, "target": { "key": "72c49ee4d0b119446c17de8cc238855847dfe2c394cecee62da90afd5c8f3d9b" } } ], "extra": [ 1, 112, 209, 66, 111, 130, 34, 243, 190, 171, 220, 101, 111, 3, 67, 21, 196, 161, 119, 39, 165, 107, 35, 205, 238, 111, 16, 32, 14, 40, 68, 237, 214, 2, 17, 0, 0, 0, 51, 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