Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7277cd0c62ba0587cbd7f67ea99ca064c680e3b719bfb5267ea9bcd1afbc490d

Tx prefix hash: faa0521fa1c756f466ab10161bf4be2691bcb6c4a32ff36c3123bf1ad5bf1b44
Tx public key: f5dc0dc12b6f038a2a128722bd2b79cf3f92143bf5c815ae5b9995de641021c9
Timestamp: 1728499291 Timestamp [UCT]: 2024-10-09 18:41:31 Age [y:d:h:m:s]: 00:189:10:28:55
Block: 1128019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135180 RingCT/type: yes/0
Extra: 01f5dc0dc12b6f038a2a128722bd2b79cf3f92143bf5c815ae5b9995de641021c902110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3585831175b93bd241c759c8a31b7f296b6e9bedc1a80956e567a439e347450 0.600000000000 1610834 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": 1128029, "vin": [ { "gen": { "height": 1128019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3585831175b93bd241c759c8a31b7f296b6e9bedc1a80956e567a439e347450" } } ], "extra": [ 1, 245, 220, 13, 193, 43, 111, 3, 138, 42, 18, 135, 34, 189, 43, 121, 207, 63, 146, 20, 59, 245, 200, 21, 174, 91, 153, 149, 222, 100, 16, 33, 201, 2, 17, 0, 0, 0, 11, 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