Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c5982c9cda01cd29f08fba10fbab5e06e6bbca473bf70f859ec23cf5ede244

Tx prefix hash: ba6b0f7a11ea3e61bc475ce5ce0df949dbd987c08aa256f2ac76a976aa82839b
Tx public key: 757a276ac04a959277dba4c8aa9a55a382e232e14f2c318b25021ddb39c4b512
Timestamp: 1737040401 Timestamp [UCT]: 2025-01-16 15:13:21 Age [y:d:h:m:s]: 00:152:02:43:44
Block: 1198678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108431 RingCT/type: yes/0
Extra: 01757a276ac04a959277dba4c8aa9a55a382e232e14f2c318b25021ddb39c4b512021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e45be55a65c934c2110dcad0228875a06580b3ad568c6a6002db39210b6069b3 0.600000000000 1685303 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": 1198688, "vin": [ { "gen": { "height": 1198678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e45be55a65c934c2110dcad0228875a06580b3ad568c6a6002db39210b6069b3" } } ], "extra": [ 1, 117, 122, 39, 106, 192, 74, 149, 146, 119, 219, 164, 200, 170, 154, 85, 163, 130, 226, 50, 225, 79, 44, 49, 139, 37, 2, 29, 219, 57, 196, 181, 18, 2, 17, 0, 0, 0, 4, 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