Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d09832a664340ca0ab7a2a2b7fca12172a5ed6beb40f22ba174065f263620117

Tx prefix hash: a6386a2531aaed831a835e9ed666b23b44ba9deac4f98fe625ab7765f964aecc
Tx public key: 4f8f3d924f587db3dbc45a5e5f7f27dc2828eb59657906356a1719ccb7e5dd82
Timestamp: 1736016142 Timestamp [UCT]: 2025-01-04 18:42:22 Age [y:d:h:m:s]: 00:164:14:39:36
Block: 1190206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117358 RingCT/type: yes/0
Extra: 014f8f3d924f587db3dbc45a5e5f7f27dc2828eb59657906356a1719ccb7e5dd8202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8155a92efc3a6d581d0d9b140cc95fae9037cee8eb1382ebea349c87f74e0ad 0.600000000000 1676721 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": 1190216, "vin": [ { "gen": { "height": 1190206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8155a92efc3a6d581d0d9b140cc95fae9037cee8eb1382ebea349c87f74e0ad" } } ], "extra": [ 1, 79, 143, 61, 146, 79, 88, 125, 179, 219, 196, 90, 94, 95, 127, 39, 220, 40, 40, 235, 89, 101, 121, 6, 53, 106, 23, 25, 204, 183, 229, 221, 130, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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