Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4a77ae4c38da0fc6156499d33591c2353dfce3b8a70d235bf0b9292e0c6974

Tx prefix hash: d719727290873258b05a9842ac0f1ad5fc3b1b8502e7538bf301d327e1aa843c
Tx public key: b4337e3bf046092684e34c38b3a7481b3092c90c170a0f468073b1e50a4336cd
Timestamp: 1726393429 Timestamp [UCT]: 2024-09-15 09:43:49 Age [y:d:h:m:s]: 00:160:11:40:47
Block: 1110559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114487 RingCT/type: yes/0
Extra: 01b4337e3bf046092684e34c38b3a7481b3092c90c170a0f468073b1e50a4336cd021100000009e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 35b4aa6abf554908dab8735afe68b434c1140032eae0d91d8bff2a862c8d02d9 0.608000000000 1589206 of 0

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": 1110569, "vin": [ { "gen": { "height": 1110559 } } ], "vout": [ { "amount": 608000000, "target": { "key": "35b4aa6abf554908dab8735afe68b434c1140032eae0d91d8bff2a862c8d02d9" } } ], "extra": [ 1, 180, 51, 126, 59, 240, 70, 9, 38, 132, 227, 76, 56, 179, 167, 72, 27, 48, 146, 201, 12, 23, 10, 15, 70, 128, 115, 177, 229, 10, 67, 54, 205, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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