Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80c73e69520d101898de7c35dee513bca36651c51eda183b60ac800789498e14

Tx prefix hash: 2cba67bf1b4b300830b024f50cc76181717ff6761a3a8f6a81b9eac48a9eeb55
Tx public key: 209e1e99d19180e25d59303e9cb4f8e91373eba9322184b217cae04d86cb60ef
Timestamp: 1739153459 Timestamp [UCT]: 2025-02-10 02:10:59 Age [y:d:h:m:s]: 00:278:21:12:30
Block: 1215903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197084 RingCT/type: yes/0
Extra: 01209e1e99d19180e25d59303e9cb4f8e91373eba9322184b217cae04d86cb60ef021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a08641dbe647e5b34c9b550800c82a2b91bf073a0a2cefca6b7519e6ff2eabe6 0.600000000000 1702702 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": 1215913, "vin": [ { "gen": { "height": 1215903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a08641dbe647e5b34c9b550800c82a2b91bf073a0a2cefca6b7519e6ff2eabe6" } } ], "extra": [ 1, 32, 158, 30, 153, 209, 145, 128, 226, 93, 89, 48, 62, 156, 180, 248, 233, 19, 115, 235, 169, 50, 33, 132, 178, 23, 202, 224, 77, 134, 203, 96, 239, 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