Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61f7eeb16c169d17d6556d5b0505916dff217130e71cbe9b1edba3f1dfde3752

Tx prefix hash: 494d61035f7e7e0150a8ed52dbb29506d61ef5b5d5ba9277f3c4e416347bbc98
Tx public key: 1babe5db0aba4246ee648c2c2d4862b0931da7d75a0ec3a1500805d92753d273
Timestamp: 1750928909 Timestamp [UCT]: 2025-06-26 09:08:29 Age [y:d:h:m:s]: 00:145:17:47:34
Block: 1313085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102152 RingCT/type: yes/0
Extra: 011babe5db0aba4246ee648c2c2d4862b0931da7d75a0ec3a1500805d92753d27302110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53aec8cfc899e904c082eb9a426c9c8d4d28095f1f566b76009a7b9e52f5b0c3 0.600000000000 1800722 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": 1313095, "vin": [ { "gen": { "height": 1313085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53aec8cfc899e904c082eb9a426c9c8d4d28095f1f566b76009a7b9e52f5b0c3" } } ], "extra": [ 1, 27, 171, 229, 219, 10, 186, 66, 70, 238, 100, 140, 44, 45, 72, 98, 176, 147, 29, 167, 215, 90, 14, 195, 161, 80, 8, 5, 217, 39, 83, 210, 115, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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