Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d6ecb6de1790801db6613bfefd7585743e6c3a3d1440f448af36d9c781e07b5

Tx prefix hash: 14d78dcd76104a398ca88af786a3f3963200d4cfee6a70233fa8a4c7f01ce85d
Tx public key: 2b2248edd3843c942addf81eaa92f9528e2d9812f8735a79956a43c3d0b92cfc
Timestamp: 1734263465 Timestamp [UCT]: 2024-12-15 11:51:05 Age [y:d:h:m:s]: 01:001:04:55:28
Block: 1175718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259263 RingCT/type: yes/0
Extra: 012b2248edd3843c942addf81eaa92f9528e2d9812f8735a79956a43c3d0b92cfc0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa46bd8b5948bc6eb2f8a7799fab8af53f4b8868a2a17db4728c7982c1daa384 0.600000000000 1662039 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": 1175728, "vin": [ { "gen": { "height": 1175718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa46bd8b5948bc6eb2f8a7799fab8af53f4b8868a2a17db4728c7982c1daa384" } } ], "extra": [ 1, 43, 34, 72, 237, 211, 132, 60, 148, 42, 221, 248, 30, 170, 146, 249, 82, 142, 45, 152, 18, 248, 115, 90, 121, 149, 106, 67, 195, 208, 185, 44, 252, 2, 17, 0, 0, 0, 3, 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