Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e26f319d7eebcd2c40a13ac47e263e1d0759fb8e0dd7723083772546a94579c

Tx prefix hash: d9a072c0416e863232703bbbfd2c20497d7b86f56d32f8d6e12b308075bddb22
Tx public key: 67f87f6b45d911dd6d0af12cdf01e2d65522a860c098433b958adbd7bfabde75
Timestamp: 1712682544 Timestamp [UCT]: 2024-04-09 17:09:04 Age [y:d:h:m:s]: 01:028:06:44:11
Block: 996870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281204 RingCT/type: yes/0
Extra: 0167f87f6b45d911dd6d0af12cdf01e2d65522a860c098433b958adbd7bfabde7502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 014026304d54b69c63d3431bc946f0ff175d6b4ce82ffc7e55bd458b3b29643d 0.600000000000 1457298 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": 996880, "vin": [ { "gen": { "height": 996870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "014026304d54b69c63d3431bc946f0ff175d6b4ce82ffc7e55bd458b3b29643d" } } ], "extra": [ 1, 103, 248, 127, 107, 69, 217, 17, 221, 109, 10, 241, 44, 223, 1, 226, 214, 85, 34, 168, 96, 192, 152, 67, 59, 149, 138, 219, 215, 191, 171, 222, 117, 2, 17, 0, 0, 0, 3, 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