Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071984b37c9b714f9e6219c819d049d98924bb6e548229218d725c825a184aa0

Tx prefix hash: 3dcaebfd2e4d7da03f2913ff055b34afb4dba72478ca9884b019d315a5c615d5
Tx public key: 0a43439b3bfb9a7abe23705f2a8c2ea3e817289ccb8af193164d67db54725624
Timestamp: 1736451221 Timestamp [UCT]: 2025-01-09 19:33:41 Age [y:d:h:m:s]: 00:160:16:40:16
Block: 1193795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114540 RingCT/type: yes/0
Extra: 010a43439b3bfb9a7abe23705f2a8c2ea3e817289ccb8af193164d67db5472562402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65ae7d4a28218fca9c790f736bbd0487c8bc158dd9fc3fa48cd81defbb5f529 0.600000000000 1680360 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": 1193805, "vin": [ { "gen": { "height": 1193795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65ae7d4a28218fca9c790f736bbd0487c8bc158dd9fc3fa48cd81defbb5f529" } } ], "extra": [ 1, 10, 67, 67, 155, 59, 251, 154, 122, 190, 35, 112, 95, 42, 140, 46, 163, 232, 23, 40, 156, 203, 138, 241, 147, 22, 77, 103, 219, 84, 114, 86, 36, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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