Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ea6eb351e1d8f2b0325397c85e95d0bdc03eed0113969b353946c1d6875041

Tx prefix hash: d3d497f149bbffcf9cc5b7c9081e2c7a360dccb5273ab62317e2c4eaab29b2e2
Tx public key: 2a904121125dd82b4d37660aca462c2faa631f14cdf2620de0899caea71f47ad
Timestamp: 1701045592 Timestamp [UCT]: 2023-11-27 00:39:52 Age [y:d:h:m:s]: 01:045:18:10:14
Block: 900408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294091 RingCT/type: yes/0
Extra: 012a904121125dd82b4d37660aca462c2faa631f14cdf2620de0899caea71f47ad021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.637638456000 dcy

stealth address amount amount idx
00: 4fa2d2b4510951be8617e9a4e5f32d1c55ae85dc64c19fd00b95d0722c734e3a 0.637638456000 1356909 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": 900418, "vin": [ { "gen": { "height": 900408 } } ], "vout": [ { "amount": 637638456, "target": { "key": "4fa2d2b4510951be8617e9a4e5f32d1c55ae85dc64c19fd00b95d0722c734e3a" } } ], "extra": [ 1, 42, 144, 65, 33, 18, 93, 216, 43, 77, 55, 102, 10, 202, 70, 44, 47, 170, 99, 31, 20, 205, 242, 98, 13, 224, 137, 156, 174, 167, 31, 71, 173, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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