Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c3e9a72cc8b47ebba4d7da2b655fe0b4431040a8f1bff9e32d1100029b23a7

Tx prefix hash: ccbf63f47f1ece737ee56f24e7044d8d2701a893291cca7aeaad57441263157f
Tx public key: f6e49b33c29a94fd5f464c4335a8960affe8cacac9c1b78bae2b65037c9a900a
Timestamp: 1732342699 Timestamp [UCT]: 2024-11-23 06:18:19 Age [y:d:h:m:s]: 00:000:22:37:43
Block: 1159786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671 RingCT/type: yes/0
Extra: 01f6e49b33c29a94fd5f464c4335a8960affe8cacac9c1b78bae2b65037c9a900a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64fd65dbeed58db43676f0c385852df9595cc320b8e78fccda8940a1023d0673 0.600000000000 1645425 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": 1159796, "vin": [ { "gen": { "height": 1159786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64fd65dbeed58db43676f0c385852df9595cc320b8e78fccda8940a1023d0673" } } ], "extra": [ 1, 246, 228, 155, 51, 194, 154, 148, 253, 95, 70, 76, 67, 53, 168, 150, 10, 255, 232, 202, 202, 201, 193, 183, 139, 174, 43, 101, 3, 124, 154, 144, 10, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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