Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26a98483eb7a8c62cb13e9960ffb4eb9d9ad999b3e515bfe2703b8da5b7c81e0

Tx prefix hash: 3561ee6ed5957f29c7da63671576a33574d7d9baf0f30bbefb6d73eaff6f28aa
Tx public key: 3385c2b67dfc2ea0b4a4330fe7cd7aacfb7d14da9ec002e51be7ba1885428aa9
Timestamp: 1699844780 Timestamp [UCT]: 2023-11-13 03:06:20 Age [y:d:h:m:s]: 01:070:07:30:40
Block: 890465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311609 RingCT/type: yes/0
Extra: 013385c2b67dfc2ea0b4a4330fe7cd7aacfb7d14da9ec002e51be7ba1885428aa902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.687891278000 dcy

stealth address amount amount idx
00: e9eb0cccaa9532c15bc992c1bad4c11a7a8219e635a85f0cdd761c53546949ba 0.687891278000 1346488 of 0

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": 890475, "vin": [ { "gen": { "height": 890465 } } ], "vout": [ { "amount": 687891278, "target": { "key": "e9eb0cccaa9532c15bc992c1bad4c11a7a8219e635a85f0cdd761c53546949ba" } } ], "extra": [ 1, 51, 133, 194, 182, 125, 252, 46, 160, 180, 164, 51, 15, 231, 205, 122, 172, 251, 125, 20, 218, 158, 192, 2, 229, 27, 231, 186, 24, 133, 66, 138, 169, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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