Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e99b1a0c1088bd630b3b02afdb6036473e572921e08e73bab06883cfb7988a9

Tx prefix hash: af5b419500eb9c18cf0348b5a361cd02f9d1f7065d01d531bde9d7cb4dec1845
Tx public key: 6413000a1081f3170940ef726bb8516e023fc00a687224d643c6bbc4ead64a0c
Timestamp: 1748311534 Timestamp [UCT]: 2025-05-27 02:05:34 Age [y:d:h:m:s]: 00:178:15:44:08
Block: 1291729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125375 RingCT/type: yes/0
Extra: 016413000a1081f3170940ef726bb8516e023fc00a687224d643c6bbc4ead64a0c02110000000286ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe74ab811b2f5682b5c118346e57296aa7b101ea9f5d7f16a8cd329459f712fd 0.600000000000 1779200 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": 1291739, "vin": [ { "gen": { "height": 1291729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe74ab811b2f5682b5c118346e57296aa7b101ea9f5d7f16a8cd329459f712fd" } } ], "extra": [ 1, 100, 19, 0, 10, 16, 129, 243, 23, 9, 64, 239, 114, 107, 184, 81, 110, 2, 63, 192, 10, 104, 114, 36, 214, 67, 198, 187, 196, 234, 214, 74, 12, 2, 17, 0, 0, 0, 2, 134, 174, 47, 13, 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