Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc957b9f380569d9370911d83f0e2ce6d1b04643fd73ce78efeac56eddb26514

Tx prefix hash: 911ed2a7f2a5255bb71f345f9c5970b34cfa95fee755fcecc128313fc72c40c5
Tx public key: 221b12f614bd67d6b17f860c5a159f13db037cb24ff8eec6fcf3c0ec748b843a
Timestamp: 1718763547 Timestamp [UCT]: 2024-06-19 02:19:07 Age [y:d:h:m:s]: 00:271:08:57:52
Block: 1047304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193934 RingCT/type: yes/0
Extra: 01221b12f614bd67d6b17f860c5a159f13db037cb24ff8eec6fcf3c0ec748b843a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab7e16ef10403a456c2df5363a248007f63b5650ab99ec41d83efae0cc33ff43 0.600000000000 1517123 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": 1047314, "vin": [ { "gen": { "height": 1047304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab7e16ef10403a456c2df5363a248007f63b5650ab99ec41d83efae0cc33ff43" } } ], "extra": [ 1, 34, 27, 18, 246, 20, 189, 103, 214, 177, 127, 134, 12, 90, 21, 159, 19, 219, 3, 124, 178, 79, 248, 238, 198, 252, 243, 192, 236, 116, 139, 132, 58, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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