Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47aa4db7ea4b1c12ba5565bc300070d22107945bf0424dea58ebc19deb8fc025

Tx prefix hash: 59b46c96d169ba14db58d1f00a9413b6c0fe73face73214e8390f3768bee9ede
Tx public key: 8a7a7c7f1d560dc4c26eb0d1b1ed4541d68659ac264b3e7e2e02dd861cc9b8b9
Timestamp: 1702401703 Timestamp [UCT]: 2023-12-12 17:21:43 Age [y:d:h:m:s]: 01:326:22:08:54
Block: 911677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492478 RingCT/type: yes/0
Extra: 018a7a7c7f1d560dc4c26eb0d1b1ed4541d68659ac264b3e7e2e02dd861cc9b8b902110000000a33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a04aca733bed05654d29900977935075dbc9e0e9fffa9642bc31af5940ab1ad2 0.600000000000 1368891 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": 911687, "vin": [ { "gen": { "height": 911677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a04aca733bed05654d29900977935075dbc9e0e9fffa9642bc31af5940ab1ad2" } } ], "extra": [ 1, 138, 122, 124, 127, 29, 86, 13, 196, 194, 110, 176, 209, 177, 237, 69, 65, 214, 134, 89, 172, 38, 75, 62, 126, 46, 2, 221, 134, 28, 201, 184, 185, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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