Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7de67293c09fb81c319ab6b0f2210d6cfe22c24a78cd41b690fcfd7e8da79a7d

Tx prefix hash: 7c6d82993e46437e6961c63ccbad201e3cc9081ed72a5c08ad9d0ea697412124
Tx public key: 1fa4ecd25ab86ff0a8a67c54d4fa5632ee4ef6fe254420a99dac310ed10d2353
Timestamp: 1729560682 Timestamp [UCT]: 2024-10-22 01:31:22 Age [y:d:h:m:s]: 01:027:23:04:57
Block: 1136776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278397 RingCT/type: yes/0
Extra: 011fa4ecd25ab86ff0a8a67c54d4fa5632ee4ef6fe254420a99dac310ed10d2353021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f43afc3690d7d50bd363f25c0d6da39c8072a2bc5d22b880d8a68a02b57d4f7e 0.600000000000 1620145 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": 1136786, "vin": [ { "gen": { "height": 1136776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f43afc3690d7d50bd363f25c0d6da39c8072a2bc5d22b880d8a68a02b57d4f7e" } } ], "extra": [ 1, 31, 164, 236, 210, 90, 184, 111, 240, 168, 166, 124, 84, 212, 250, 86, 50, 238, 78, 246, 254, 37, 68, 32, 169, 157, 172, 49, 14, 209, 13, 35, 83, 2, 17, 0, 0, 0, 2, 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