Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353b1308b02b535a7cc05a2879105e56116ef89a80aa77710a57fe85b316faf3

Tx prefix hash: 733c84633378fce4b81540cd6ddf5ac70b604f2f48c72045ed1bdc64ff153114
Tx public key: f34edf99150b048b1361b3c9ac6112b6d86095e3f23dcc17cc6cd8600ef4bf3a
Timestamp: 1694638753 Timestamp [UCT]: 2023-09-13 20:59:13 Age [y:d:h:m:s]: 01:201:18:43:40
Block: 847484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405310 RingCT/type: yes/0
Extra: 01f34edf99150b048b1361b3c9ac6112b6d86095e3f23dcc17cc6cd8600ef4bf3a02110000000433af99f4000000000000000000

1 output(s) for total of 0.954846941000 dcy

stealth address amount amount idx
00: bd24f748d734706671a860dab28cdc810b3f4e901644b5f6ae9ab1d0f1570d6a 0.954846941000 1301010 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": 847494, "vin": [ { "gen": { "height": 847484 } } ], "vout": [ { "amount": 954846941, "target": { "key": "bd24f748d734706671a860dab28cdc810b3f4e901644b5f6ae9ab1d0f1570d6a" } } ], "extra": [ 1, 243, 78, 223, 153, 21, 11, 4, 139, 19, 97, 179, 201, 172, 97, 18, 182, 216, 96, 149, 227, 242, 61, 204, 23, 204, 108, 216, 96, 14, 244, 191, 58, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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