Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f6b227ed8ec68852d455431b29bc3a991be33e1c8de5f3fd76b86a7a8c27d0

Tx prefix hash: 0d46277dff6a1d57c6bfd38bc6e43d37c8225a84b18f1fe1374749aeb2bb09e8
Tx public key: 406c35b6a439a04b5bfb110b36b1f0a9f3d7ad0fb2c8268e8ab479e94ba977d5
Timestamp: 1712279821 Timestamp [UCT]: 2024-04-05 01:17:01 Age [y:d:h:m:s]: 01:000:01:37:04
Block: 993533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261013 RingCT/type: yes/0
Extra: 01406c35b6a439a04b5bfb110b36b1f0a9f3d7ad0fb2c8268e8ab479e94ba977d502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efcc691035f0ba56128b829bae714fd01e7d99d0cc3f2bbd38f2f3a734794dba 0.600000000000 1453919 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": 993543, "vin": [ { "gen": { "height": 993533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efcc691035f0ba56128b829bae714fd01e7d99d0cc3f2bbd38f2f3a734794dba" } } ], "extra": [ 1, 64, 108, 53, 182, 164, 57, 160, 75, 91, 251, 17, 11, 54, 177, 240, 169, 243, 215, 173, 15, 178, 200, 38, 142, 138, 180, 121, 233, 75, 169, 119, 213, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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