Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0abffc7376430abb5674b6bae1af2b5fdad23ad1c3de4a3b5cdb71ff5a849b

Tx prefix hash: 8ffb79bdd4372615b5a91e2ab03070e2d2f9071ce18d49e12230609848956140
Tx public key: 8430153b5c43056f8d324b70c8b46c7f31f54934e29a8b2e4a4a1cca80faee0f
Timestamp: 1736863667 Timestamp [UCT]: 2025-01-14 14:07:47 Age [y:d:h:m:s]: 00:335:23:59:19
Block: 1197221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237674 RingCT/type: yes/0
Extra: 018430153b5c43056f8d324b70c8b46c7f31f54934e29a8b2e4a4a1cca80faee0f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11b2903368dde7261878b63ecdedf302f1acafcdeaa987db8a338a03c3961fe6 0.600000000000 1683828 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": 1197231, "vin": [ { "gen": { "height": 1197221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11b2903368dde7261878b63ecdedf302f1acafcdeaa987db8a338a03c3961fe6" } } ], "extra": [ 1, 132, 48, 21, 59, 92, 67, 5, 111, 141, 50, 75, 112, 200, 180, 108, 127, 49, 245, 73, 52, 226, 154, 139, 46, 74, 74, 28, 202, 128, 250, 238, 15, 2, 17, 0, 0, 0, 5, 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