Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2385fd11e93fb3a64b5b8705ec40d7d1bd73b20e629f5000758c076dbff28007

Tx prefix hash: e3a6e1b86d2a8a5f42e1dbd8166179ace15abf41f6452c961b7757ab45760286
Tx public key: cd5ce748bd5db6ef2965d8e5c9c18759ef78b481d8e68f69f34df3fbe06f8c7e
Timestamp: 1673976543 Timestamp [UCT]: 2023-01-17 17:29:03 Age [y:d:h:m:s]: 02:042:03:11:35
Block: 676866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551737 RingCT/type: yes/0
Extra: 01cd5ce748bd5db6ef2965d8e5c9c18759ef78b481d8e68f69f34df3fbe06f8c7e021100000002faf35c9c000000000000000000

1 output(s) for total of 3.509634647000 dcy

stealth address amount amount idx
00: c2f938d0df416fdeb2aac0c011ff362d06c361612c9b721d43b407105a153855 3.509634647000 1118621 of 0

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": 676876, "vin": [ { "gen": { "height": 676866 } } ], "vout": [ { "amount": 3509634647, "target": { "key": "c2f938d0df416fdeb2aac0c011ff362d06c361612c9b721d43b407105a153855" } } ], "extra": [ 1, 205, 92, 231, 72, 189, 93, 182, 239, 41, 101, 216, 229, 201, 193, 135, 89, 239, 120, 180, 129, 216, 230, 143, 105, 243, 77, 243, 251, 224, 111, 140, 126, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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