Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2880fdf554197b116ae48025dc2401d487d286ba023d3079929e64c10235ef

Tx prefix hash: ebb78fa39c38559f467b8e1838b6817013bced9862e65d08a773b25cf2dd25a2
Tx public key: b70c5233d47e731d74d58ead8f2ddd2620dfd90a44cffb171d6195dd1889e6ba
Timestamp: 1733688666 Timestamp [UCT]: 2024-12-08 20:11:06 Age [y:d:h:m:s]: 00:123:08:46:11
Block: 1170957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87955 RingCT/type: yes/0
Extra: 01b70c5233d47e731d74d58ead8f2ddd2620dfd90a44cffb171d6195dd1889e6ba021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aac1efc7be5c0e37f9802f7eccb463783b3142c1be2e654c55fca59b6974ae6 0.600000000000 1656692 of 15

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": 1170967, "vin": [ { "gen": { "height": 1170957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aac1efc7be5c0e37f9802f7eccb463783b3142c1be2e654c55fca59b6974ae6" } } ], "extra": [ 1, 183, 12, 82, 51, 212, 126, 115, 29, 116, 213, 142, 173, 143, 45, 221, 38, 32, 223, 217, 10, 68, 207, 251, 23, 29, 97, 149, 221, 24, 137, 230, 186, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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