Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8c2e8cd79eb7c00fad4b7659ae7e02e07bc7117baef1d890b81c7a4eeacc2c6

Tx prefix hash: 6696c70465b74653e0079853882e738735e78563728abf26614c8d6ce783ab64
Tx public key: c58ba61c45d32f3ea9207e5cdfa053d3557e1e900f1128ead3936cd0c6dd7e8a
Timestamp: 1732447334 Timestamp [UCT]: 2024-11-24 11:22:14 Age [y:d:h:m:s]: 00:182:04:24:58
Block: 1160649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130068 RingCT/type: yes/0
Extra: 01c58ba61c45d32f3ea9207e5cdfa053d3557e1e900f1128ead3936cd0c6dd7e8a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 498966f9bd8e778896695f3ac14ad4e8b7d38a36711c51c78bbeb89c77f26daf 0.600000000000 1646298 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": 1160659, "vin": [ { "gen": { "height": 1160649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "498966f9bd8e778896695f3ac14ad4e8b7d38a36711c51c78bbeb89c77f26daf" } } ], "extra": [ 1, 197, 139, 166, 28, 69, 211, 47, 62, 169, 32, 126, 92, 223, 160, 83, 211, 85, 126, 30, 144, 15, 17, 40, 234, 211, 147, 108, 208, 198, 221, 126, 138, 2, 17, 0, 0, 0, 5, 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