Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7931a12d24ec5466c4e773a41dbef5991e9705780cb92444273d8e9f77abc2d

Tx prefix hash: 55ab5a039659e281201fc06c3816cb361e46994b3338335628eac7876b3fa311
Tx public key: 25cb1b4ea110d069add6e9129a0de47c2374faf39a3845cc9d8e3cfbb6e82199
Timestamp: 1736151929 Timestamp [UCT]: 2025-01-06 08:25:29 Age [y:d:h:m:s]: 00:162:07:56:04
Block: 1191339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115723 RingCT/type: yes/0
Extra: 0125cb1b4ea110d069add6e9129a0de47c2374faf39a3845cc9d8e3cfbb6e821990211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a13ccb6869265f8b9e258c1bf882432a0809ee6bd15b6fcb510dc435c355c651 0.600000000000 1677864 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": 1191349, "vin": [ { "gen": { "height": 1191339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a13ccb6869265f8b9e258c1bf882432a0809ee6bd15b6fcb510dc435c355c651" } } ], "extra": [ 1, 37, 203, 27, 78, 161, 16, 208, 105, 173, 214, 233, 18, 154, 13, 228, 124, 35, 116, 250, 243, 154, 56, 69, 204, 157, 142, 60, 251, 182, 232, 33, 153, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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