Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6eba49d51b9810652c4412328f77303d58071746724bbcbe9b133f5e3e30ce2

Tx prefix hash: 34c0f25c32395bf619af94a91d5cab4cd923093009456f2a60b549688f6a5115
Tx public key: 0688f5fe830fc8efb2d0d5c342a64845f89b8f34fcf2e4fed37987ba8f0f118f
Timestamp: 1745681926 Timestamp [UCT]: 2025-04-26 15:38:46 Age [y:d:h:m:s]: 00:209:02:11:50
Block: 1269961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147144 RingCT/type: yes/0
Extra: 010688f5fe830fc8efb2d0d5c342a64845f89b8f34fcf2e4fed37987ba8f0f118f02110000000fdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7b8bb0aef87ff801040d9b8d3fe7f97c9cf3a63915b04234f8fa0a8b60ebb4e 0.600000000000 1757200 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": 1269971, "vin": [ { "gen": { "height": 1269961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7b8bb0aef87ff801040d9b8d3fe7f97c9cf3a63915b04234f8fa0a8b60ebb4e" } } ], "extra": [ 1, 6, 136, 245, 254, 131, 15, 200, 239, 178, 208, 213, 195, 66, 166, 72, 69, 248, 155, 143, 52, 252, 242, 228, 254, 211, 121, 135, 186, 143, 15, 17, 143, 2, 17, 0, 0, 0, 15, 219, 181, 113, 193, 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