Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a98d10f866201a883fa70dd35f84d60357b562c9549db006a81ea7d0f5bb6ebf

Tx prefix hash: c6f1275dcf0de29a8e7c1c2c5bc9793d08d99315116a3e0060f2c846f1f3d569
Tx public key: 046e6dcd6827990d4fdbb9c3c32ebe037aedd03d4617d6f9b14a6873e24030b1
Timestamp: 1748079247 Timestamp [UCT]: 2025-05-24 09:34:07 Age [y:d:h:m:s]: 00:229:01:11:18
Block: 1289817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161460 RingCT/type: yes/0
Extra: 01046e6dcd6827990d4fdbb9c3c32ebe037aedd03d4617d6f9b14a6873e24030b1021100000007a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4129dc73263c87ddafe46ca8674f11f9e01369389e925dae1c33a19cbfc29890 0.600000000000 1777286 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": 1289827, "vin": [ { "gen": { "height": 1289817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4129dc73263c87ddafe46ca8674f11f9e01369389e925dae1c33a19cbfc29890" } } ], "extra": [ 1, 4, 110, 109, 205, 104, 39, 153, 13, 79, 219, 185, 195, 195, 46, 190, 3, 122, 237, 208, 61, 70, 23, 214, 249, 177, 74, 104, 115, 226, 64, 48, 177, 2, 17, 0, 0, 0, 7, 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