Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b74bebd4cbaa60a4900e7566e01a896adbec196e3160a3fd320ffa59e47f0429

Tx prefix hash: 9a8b05f71485aceecb43dbee290d06e38568dcf1f70fd71b4f02d88aa363003b
Tx public key: f2c7c9f8ff546a0b98989a342924f3ccd714b6bf5f7e1bc5c94796cd3ec40d9f
Timestamp: 1733330108 Timestamp [UCT]: 2024-12-04 16:35:08 Age [y:d:h:m:s]: 00:159:07:53:18
Block: 1167961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113697 RingCT/type: yes/0
Extra: 01f2c7c9f8ff546a0b98989a342924f3ccd714b6bf5f7e1bc5c94796cd3ec40d9f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9030d26332a7f1d8c99cea43c822d7bf33f2cff48f0c7a4be9c03a47bc6167a 0.600000000000 1653666 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": 1167971, "vin": [ { "gen": { "height": 1167961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9030d26332a7f1d8c99cea43c822d7bf33f2cff48f0c7a4be9c03a47bc6167a" } } ], "extra": [ 1, 242, 199, 201, 248, 255, 84, 106, 11, 152, 152, 154, 52, 41, 36, 243, 204, 215, 20, 182, 191, 95, 126, 27, 197, 201, 71, 150, 205, 62, 196, 13, 159, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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