Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddd5891ba2eeef256bf2c1174f4c6beccdb4b56b24062224d86322e5205d8485

Tx prefix hash: b7c36bfebf295b8769a051ec69b2bd1c1c7c6b1493f42503a10d97b67b7c3e41
Tx public key: e448eb70e25efc41a971454b53f8a6fd91fb94e1f55584eafcea449f24abcdca
Timestamp: 1727989728 Timestamp [UCT]: 2024-10-03 21:08:48 Age [y:d:h:m:s]: 00:051:20:44:41
Block: 1123800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37044 RingCT/type: yes/0
Extra: 01e448eb70e25efc41a971454b53f8a6fd91fb94e1f55584eafcea449f24abcdca02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fff6b6bc2d2fe8cbdf0b6e689fb82e36e00c2e50f476a5a63499602aa0210753 0.600000000000 1606335 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": 1123810, "vin": [ { "gen": { "height": 1123800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fff6b6bc2d2fe8cbdf0b6e689fb82e36e00c2e50f476a5a63499602aa0210753" } } ], "extra": [ 1, 228, 72, 235, 112, 226, 94, 252, 65, 169, 113, 69, 75, 83, 248, 166, 253, 145, 251, 148, 225, 245, 85, 132, 234, 252, 234, 68, 159, 36, 171, 205, 202, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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