Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a8147eccf8cd27b6a970cd343c395d6613df1e537c58f0ecc6e15b795d7c99d

Tx prefix hash: 849ac76bfa45f82f7b78e0d3ed35e19739dba200c0ee1e9f191cdb4055942e09
Tx public key: 634f542d6b9a936cd9b92fdb12065942bd9c27be5b92ffdf1a4c7913bc9ce4ba
Timestamp: 1723325259 Timestamp [UCT]: 2024-08-10 21:27:39 Age [y:d:h:m:s]: 00:266:00:27:29
Block: 1085128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190025 RingCT/type: yes/0
Extra: 01634f542d6b9a936cd9b92fdb12065942bd9c27be5b92ffdf1a4c7913bc9ce4ba021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59bf2d18e69da4fe38dbc35ff0d7f5281f137e6613801018989ff63e0d6c19e1 0.600000000000 1559637 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": 1085138, "vin": [ { "gen": { "height": 1085128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59bf2d18e69da4fe38dbc35ff0d7f5281f137e6613801018989ff63e0d6c19e1" } } ], "extra": [ 1, 99, 79, 84, 45, 107, 154, 147, 108, 217, 185, 47, 219, 18, 6, 89, 66, 189, 156, 39, 190, 91, 146, 255, 223, 26, 76, 121, 19, 188, 156, 228, 186, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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