Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a00263d7b6e3a845f72e8d86c58d1c1d43b4abb2e076d574e439787b270f122

Tx prefix hash: 85f874469de2118b5cbb64d586d8d2984b25772ef720fb7ee0b2cbabe197139c
Tx public key: 53e940c34f486f9bbd15081af2003bf5d4afa48ae0ccbd1552753e3e7b5689ae
Timestamp: 1737407038 Timestamp [UCT]: 2025-01-20 21:03:58 Age [y:d:h:m:s]: 00:150:08:30:47
Block: 1201679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107181 RingCT/type: yes/0
Extra: 0153e940c34f486f9bbd15081af2003bf5d4afa48ae0ccbd1552753e3e7b5689ae021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b79969317e606e4a5725e72820afe7a52b147e9f7a8f1e4e665cc5db48e0565 0.600000000000 1688336 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": 1201689, "vin": [ { "gen": { "height": 1201679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b79969317e606e4a5725e72820afe7a52b147e9f7a8f1e4e665cc5db48e0565" } } ], "extra": [ 1, 83, 233, 64, 195, 79, 72, 111, 155, 189, 21, 8, 26, 242, 0, 59, 245, 212, 175, 164, 138, 224, 204, 189, 21, 82, 117, 62, 62, 123, 86, 137, 174, 2, 17, 0, 0, 0, 9, 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