Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e20e62153f0ab2c80f39a7cff9798bf40fa6d2fbe5c947adfaff468c22c1f3c

Tx prefix hash: 82a5cba1fb075d864fab041f2cf0f13e28e90f4472ec154ad7c09f534f2f4320
Tx public key: b413158929297a14450635a84253c2518a16c97609c40b106f5a07b0c820e01e
Timestamp: 1722636087 Timestamp [UCT]: 2024-08-02 22:01:27 Age [y:d:h:m:s]: 00:082:18:34:36
Block: 1079406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59251 RingCT/type: yes/0
Extra: 01b413158929297a14450635a84253c2518a16c97609c40b106f5a07b0c820e01e02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a6e0fb541197b25a99c2a4f718e59b196d2040170c1ccdb91dd0ddbfe3ca969 0.600000000000 1552349 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": 1079416, "vin": [ { "gen": { "height": 1079406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a6e0fb541197b25a99c2a4f718e59b196d2040170c1ccdb91dd0ddbfe3ca969" } } ], "extra": [ 1, 180, 19, 21, 137, 41, 41, 122, 20, 69, 6, 53, 168, 66, 83, 194, 81, 138, 22, 201, 118, 9, 196, 11, 16, 111, 90, 7, 176, 200, 32, 224, 30, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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