Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5902adb2f0776adcc171af0686288480da9a1735a2dc44e40c08eb7e3ec5d02

Tx prefix hash: b1820f05098e6ad749e3dfd421409f41660b1b9317ef1039dbb97ec3ada8e523
Tx public key: bf74e1d60b066082136867eff5dcbe06d8e0539ebae52d34302661b7e57f52f5
Timestamp: 1673083163 Timestamp [UCT]: 2023-01-07 09:19:23 Age [y:d:h:m:s]: 02:011:14:20:56
Block: 669442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530205 RingCT/type: yes/0
Extra: 01bf74e1d60b066082136867eff5dcbe06d8e0539ebae52d34302661b7e57f52f502110000000152542ceb000000000000000000

1 output(s) for total of 3.714160898000 dcy

stealth address amount amount idx
00: d910e0e8df06e9e6fd0a065f77fa154c7617b4fc477e8deaddad9fa7df108959 3.714160898000 1110759 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": 669452, "vin": [ { "gen": { "height": 669442 } } ], "vout": [ { "amount": 3714160898, "target": { "key": "d910e0e8df06e9e6fd0a065f77fa154c7617b4fc477e8deaddad9fa7df108959" } } ], "extra": [ 1, 191, 116, 225, 214, 11, 6, 96, 130, 19, 104, 103, 239, 245, 220, 190, 6, 216, 224, 83, 158, 186, 229, 45, 52, 48, 38, 97, 183, 229, 127, 82, 245, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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