Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c66c5e7bc0d8f9c6528b2aed01db71241e3f2c68894130b5ae55dbf59cfcf896

Tx prefix hash: 330c56dc048d5a950a705242b549d7a8391f9e84b7e6f89e9ff8aff3cf498783
Tx public key: ae870c1c7b29e01db579d7fedc1122929a4fa91c71db491c4c96a3b438a48e42
Timestamp: 1711549176 Timestamp [UCT]: 2024-03-27 14:19:36 Age [y:d:h:m:s]: 01:003:20:39:26
Block: 987520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263699 RingCT/type: yes/0
Extra: 01ae870c1c7b29e01db579d7fedc1122929a4fa91c71db491c4c96a3b438a48e420211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00e9ec8661aa48d1f466a05c8434ca8997599d912e211cbe3063a650df6c7f58 0.600000000000 1447771 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": 987530, "vin": [ { "gen": { "height": 987520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00e9ec8661aa48d1f466a05c8434ca8997599d912e211cbe3063a650df6c7f58" } } ], "extra": [ 1, 174, 135, 12, 28, 123, 41, 224, 29, 181, 121, 215, 254, 220, 17, 34, 146, 154, 79, 169, 28, 113, 219, 73, 28, 76, 150, 163, 180, 56, 164, 142, 66, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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