Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cf10ccc5b2e178290715c457c61210073d43b82f7d2b04d36041f30152f155e

Tx prefix hash: 61f058b9cf8ad7fea4a9b522b58fd273545d334621bb5f50ccaa01902b20d247
Tx public key: a6ca3975db5e9463d6289e6703541bf29f5440c354b962287a8cb7c5a90ec315
Timestamp: 1716374956 Timestamp [UCT]: 2024-05-22 10:49:16 Age [y:d:h:m:s]: 00:195:08:48:49
Block: 1027507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139836 RingCT/type: yes/0
Extra: 01a6ca3975db5e9463d6289e6703541bf29f5440c354b962287a8cb7c5a90ec3150211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ab6468f38e009b6b3b75d3114362f20b7467cea2f74d0aaaef010a3049f2d55 0.600000000000 1495162 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": 1027517, "vin": [ { "gen": { "height": 1027507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ab6468f38e009b6b3b75d3114362f20b7467cea2f74d0aaaef010a3049f2d55" } } ], "extra": [ 1, 166, 202, 57, 117, 219, 94, 148, 99, 214, 40, 158, 103, 3, 84, 27, 242, 159, 84, 64, 195, 84, 185, 98, 40, 122, 140, 183, 197, 169, 14, 195, 21, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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