Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c24b91ef0c9d8f94508251f9fb9b7ef3da19cdbdc2e9b932274adb7f701a0ca

Tx prefix hash: fcb8201945e2022266893786392d6595eeeaa7f5047b277265806d522f553579
Tx public key: 41c428309bc6698f7e7d4f22d83e4a0aa4462bea205e68eb8969989eb1fd538f
Timestamp: 1708834229 Timestamp [UCT]: 2024-02-25 04:10:29 Age [y:d:h:m:s]: 01:039:10:09:40
Block: 964990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289190 RingCT/type: yes/0
Extra: 0141c428309bc6698f7e7d4f22d83e4a0aa4462bea205e68eb8969989eb1fd538f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14ef0fed12f4639a497032ad366e038a47c9aeae553077de9472edba71d4aebf 0.600000000000 1424735 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": 965000, "vin": [ { "gen": { "height": 964990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14ef0fed12f4639a497032ad366e038a47c9aeae553077de9472edba71d4aebf" } } ], "extra": [ 1, 65, 196, 40, 48, 155, 198, 105, 143, 126, 125, 79, 34, 216, 62, 74, 10, 164, 70, 43, 234, 32, 94, 104, 235, 137, 105, 152, 158, 177, 253, 83, 143, 2, 17, 0, 0, 0, 6, 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