Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a604dcad4169fcfa2e2c20b5166f973c613cfb320c99ec987f935229a6d2ac8b

Tx prefix hash: dc7f2e70b5cdd86356c104500259dab70187014bdcd2dbdc2de330175db310c1
Tx public key: a4c6ec5ebb78f90f7da0643b61aa0f04e99ea1a4684c3e80cab531448e8a9c8d
Timestamp: 1700203413 Timestamp [UCT]: 2023-11-17 06:43:33 Age [y:d:h:m:s]: 01:065:18:59:14
Block: 893429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308385 RingCT/type: yes/0
Extra: 01a4c6ec5ebb78f90f7da0643b61aa0f04e99ea1a4684c3e80cab531448e8a9c8d021100000002faf35c9c000000000000000000

1 output(s) for total of 0.672510139000 dcy

stealth address amount amount idx
00: 3f8256b949c03c1b3eeafb4c0e3f8988c3f9de0f61277723aa90c2371832c01d 0.672510139000 1349594 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": 893439, "vin": [ { "gen": { "height": 893429 } } ], "vout": [ { "amount": 672510139, "target": { "key": "3f8256b949c03c1b3eeafb4c0e3f8988c3f9de0f61277723aa90c2371832c01d" } } ], "extra": [ 1, 164, 198, 236, 94, 187, 120, 249, 15, 125, 160, 100, 59, 97, 170, 15, 4, 233, 158, 161, 164, 104, 76, 62, 128, 202, 181, 49, 68, 142, 138, 156, 141, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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