Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a925e9515ccdd838e2059b3d7109acd243ef94e57348f9a047693070405e06a2

Tx prefix hash: b0857b140d9501a4aa6f639085b2e8091eb38a669134a511fef0adca7ff218a7
Tx public key: 9f5ed7291e6b8e319e8a112f4aca500cf9536c3dccad3fd7ab78b5fbe95a7a4a
Timestamp: 1674169246 Timestamp [UCT]: 2023-01-19 23:00:46 Age [y:d:h:m:s]: 02:149:19:15:38
Block: 678460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 628653 RingCT/type: yes/0
Extra: 019f5ed7291e6b8e319e8a112f4aca500cf9536c3dccad3fd7ab78b5fbe95a7a4a02110000000875e3f0e9000000000000000000

1 output(s) for total of 3.467211406000 dcy

stealth address amount amount idx
00: a5c3b0d3dba16fe5e494c51d30d1c550d4eb0f6f56d3761b38d456a16117bfd9 3.467211406000 1120343 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": 678470, "vin": [ { "gen": { "height": 678460 } } ], "vout": [ { "amount": 3467211406, "target": { "key": "a5c3b0d3dba16fe5e494c51d30d1c550d4eb0f6f56d3761b38d456a16117bfd9" } } ], "extra": [ 1, 159, 94, 215, 41, 30, 107, 142, 49, 158, 138, 17, 47, 74, 202, 80, 12, 249, 83, 108, 61, 204, 173, 63, 215, 171, 120, 181, 251, 233, 90, 122, 74, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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