Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1336824c02ee54bb999aaae476ead6450ba6f156e5d1813876e41ce26d04bc4

Tx prefix hash: c2adce207f4ce3e11f8b1d7786bf8e312f3d3ffaf0575c57230c608378ae0aae
Tx public key: b1f3b7bb039e5430d1fce7fafd7322326b065697476c54e3bf5e3bba9baa3806
Timestamp: 1705110056 Timestamp [UCT]: 2024-01-13 01:40:56 Age [y:d:h:m:s]: 01:113:10:37:30
Block: 934089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342205 RingCT/type: yes/0
Extra: 01b1f3b7bb039e5430d1fce7fafd7322326b065697476c54e3bf5e3bba9baa38060211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0562d1ee9aa7ff847f346c075a5da34bc8f8523fd476991305dbd1609abebe80 0.600000000000 1392075 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": 934099, "vin": [ { "gen": { "height": 934089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0562d1ee9aa7ff847f346c075a5da34bc8f8523fd476991305dbd1609abebe80" } } ], "extra": [ 1, 177, 243, 183, 187, 3, 158, 84, 48, 209, 252, 231, 250, 253, 115, 34, 50, 107, 6, 86, 151, 71, 108, 84, 227, 191, 94, 59, 186, 155, 170, 56, 6, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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