Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae21b4ce7cf490dcaefa4d71fa392012d0e15d57c2d1a042fe456d6abe2efd08

Tx prefix hash: 0068a648d7962184df4c819965d56185978c6a06286fb2cc8c17a24598e1b6b3
Tx public key: 6d26e56090c0b089442adcac45f9117a0980a96a1c4585bd1ba57b206b5e625f
Timestamp: 1738381181 Timestamp [UCT]: 2025-02-01 03:39:41 Age [y:d:h:m:s]: 00:325:16:55:04
Block: 1209519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230582 RingCT/type: yes/0
Extra: 016d26e56090c0b089442adcac45f9117a0980a96a1c4585bd1ba57b206b5e625f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a14bbf359462f219dd02f1f2a70af13b92db6242b1265cdb8101b8a361ef63a 0.600000000000 1696260 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": 1209529, "vin": [ { "gen": { "height": 1209519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a14bbf359462f219dd02f1f2a70af13b92db6242b1265cdb8101b8a361ef63a" } } ], "extra": [ 1, 109, 38, 229, 96, 144, 192, 176, 137, 68, 42, 220, 172, 69, 249, 17, 122, 9, 128, 169, 106, 28, 69, 133, 189, 27, 165, 123, 32, 107, 94, 98, 95, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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