Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c2de6f5103e02bc62d2959e2c13be4de1393be7f63243a9128d6e81b29214d0

Tx prefix hash: 932c88432db215b4ff4254274c91e2834323b4d364469113f3781ffa8f8f041c
Tx public key: d4554336ccd5b5b22f0230bed528132f8d5759c21c00977e604c2dffd68b7036
Timestamp: 1706358545 Timestamp [UCT]: 2024-01-27 12:29:05 Age [y:d:h:m:s]: 01:072:18:13:39
Block: 944439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313085 RingCT/type: yes/0
Extra: 01d4554336ccd5b5b22f0230bed528132f8d5759c21c00977e604c2dffd68b703602110000000510a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c7e4621a132ab613d5e8f1daae9b7067cc6c7071fa9e8299d2ef50fd467b4e 0.600000000000 1402675 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": 944449, "vin": [ { "gen": { "height": 944439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c7e4621a132ab613d5e8f1daae9b7067cc6c7071fa9e8299d2ef50fd467b4e" } } ], "extra": [ 1, 212, 85, 67, 54, 204, 213, 181, 178, 47, 2, 48, 190, 213, 40, 19, 47, 141, 87, 89, 194, 28, 0, 151, 126, 96, 76, 45, 255, 214, 139, 112, 54, 2, 17, 0, 0, 0, 5, 16, 161, 116, 143, 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