Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4e775f508d635590d9d136f818d979116f4572ba34752a42e2e39acce980a2

Tx prefix hash: 68cf4f2c63511e0164c901b5843500928d0e9c90c5eba6592ed0569dc9db6c18
Tx public key: b9e33e3084c8e29960415fd34ac2a021b7ffba0e5ccbd043401057d68b7aa0e8
Timestamp: 1713245145 Timestamp [UCT]: 2024-04-16 05:25:45 Age [y:d:h:m:s]: 01:229:19:09:27
Block: 1001538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422938 RingCT/type: yes/0
Extra: 01b9e33e3084c8e29960415fd34ac2a021b7ffba0e5ccbd043401057d68b7aa0e802110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e49f126919661e050a5be737f3dc65ce82ac2ac9d611381d9a07f66eb951b87 0.600000000000 1462044 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": 1001548, "vin": [ { "gen": { "height": 1001538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e49f126919661e050a5be737f3dc65ce82ac2ac9d611381d9a07f66eb951b87" } } ], "extra": [ 1, 185, 227, 62, 48, 132, 200, 226, 153, 96, 65, 95, 211, 74, 194, 160, 33, 183, 255, 186, 14, 92, 203, 208, 67, 64, 16, 87, 214, 139, 122, 160, 232, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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