Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ddf77f754672b20288fcd164d989fd9106d3b41895670e69d0f4514108c9506

Tx prefix hash: 58a6c0c360661c89cdd6e5c82b4a98ce715b63166e028e487880c5b24e8e096f
Tx public key: ff8c15e83a0912d3f6699747c3d2cf67f7999f90c7ca2470045d598fa8a7a002
Timestamp: 1717699347 Timestamp [UCT]: 2024-06-06 18:42:27 Age [y:d:h:m:s]: 00:209:23:06:02
Block: 1038484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150262 RingCT/type: yes/0
Extra: 01ff8c15e83a0912d3f6699747c3d2cf67f7999f90c7ca2470045d598fa8a7a002021100000003d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 842c55f8bdd9d02ae035fefe5952c7c6fc1c1fcc1cc5e608bd514c09a59bd2d5 0.600000000000 1507045 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": 1038494, "vin": [ { "gen": { "height": 1038484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "842c55f8bdd9d02ae035fefe5952c7c6fc1c1fcc1cc5e608bd514c09a59bd2d5" } } ], "extra": [ 1, 255, 140, 21, 232, 58, 9, 18, 211, 246, 105, 151, 71, 195, 210, 207, 103, 247, 153, 159, 144, 199, 202, 36, 112, 4, 93, 89, 143, 168, 167, 160, 2, 2, 17, 0, 0, 0, 3, 215, 73, 245, 17, 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