Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b7aa6492c0d87c8d0c7c3a258744a70109b233826f791fbc7c59e9b3919f10

Tx prefix hash: 8b1d845d0cda9fd6040f18bcf0a0f55b2e0852e54dffec987c10fd9e2f072280
Tx public key: 40bf0e43d0addf967eb6f8d50f43d634f1fed1fe197a01746cfa9049cf1aafff
Timestamp: 1737985961 Timestamp [UCT]: 2025-01-27 13:52:41 Age [y:d:h:m:s]: 00:145:03:22:12
Block: 1206262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103629 RingCT/type: yes/0
Extra: 0140bf0e43d0addf967eb6f8d50f43d634f1fed1fe197a01746cfa9049cf1aafff021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60550256224747881b896468836b50ab6bd9df015e2040dfcd74705332ef2308 0.600000000000 1692965 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": 1206272, "vin": [ { "gen": { "height": 1206262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60550256224747881b896468836b50ab6bd9df015e2040dfcd74705332ef2308" } } ], "extra": [ 1, 64, 191, 14, 67, 208, 173, 223, 150, 126, 182, 248, 213, 15, 67, 214, 52, 241, 254, 209, 254, 25, 122, 1, 116, 108, 250, 144, 73, 207, 26, 175, 255, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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